Note

Medium Risk
Changes which paywall partials apply at runtime when state conditions are used; logic is localized and heavily tested but directly affects presented UI.

Overview
State-based component overrides now participate in buildPresentedPartial instead of being ignored. ConditionContext gains a stateReader: (String) -> JsonPrimitive? hook (default no-op) so override resolution can read paywall state by key; production callers are expected to wire this from the state store so Compose can subscribe per key inside derivedStateOf.

ComponentOverride.Condition.State evaluates equals / not-equals against the reader result: string and boolean comparisons are strict; numbers use epsilon matching so integer conditions can match double-stored values. If the key is missing (reader returns null), the override never applies for either operator. Stored values take precedence over defaults when the reader implements that merge.

Parameterized tests cover booleans, strings, numbers, defaults, type mismatch, and undeclared keys.

^{Reviewed by Cursor Bugbot for commit e471070. Bugbot is set up for automated code reviews on this repo. Configure here.}